-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merging approved edits into master #33
Closed
+4,716
−5,741
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
merge updates
definitions into a separate document.
vocabulary definition to the activitystream2-vocabulary document, begin extracting out the best practices information to a separate document.
objects. Specifically: - Define the relationship between "id", "url", "self", "alternate" and other types of links - Define some best practices for consistent / interoperable use of links - Define url as being an IRI/URI only, not a Link Value
could... existing JSON-LD parsers do not handle it well
"as:result". Used to indicate the activity for which the object or link is a result. See #20
these to the vocab just yet tho... they're just in the @context
#24 (comment) omment-58074056 This does several things: 1. It outlines a clearer separation between as:Object and as:Link 2. It models as:Link in much the same way that hydra:Link is defined, using it as a marker to indicate that the @id is dereferencable 3. It specifically handles the case where a JSON-LD object is defined as both an Object and a Link (e.g. "@type": ["as:Link", "urn:foo:object"]) For anyone looking at this without JSON-LD glasses on, this might look strange, but it works. Compatibility with AS 1.0 is preserved and people who want to use the JSON only model (without the additional -LD stuff) can continue to do so without any additional complication.
and verb blank nodes 2. Fix Pat Cappelaere's name in the acknowledgements per his request 3. Adding W3C basic geo and geosparql to initial context
- trailing "f" in a json example - "widht" => "width" - Add > after James Snell's email address
Fix a few simple typos
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.